Skip to content

Conversation

@antonis
Copy link
Contributor

@antonis antonis commented Nov 25, 2025

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

Fixes Object.freeze type pollution from @sentry-internal/replay

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing
  • No breaking changes

🔮 Next steps

@github-actions
Copy link
Contributor

github-actions bot commented Nov 25, 2025

Fails
🚫 Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

Generated by 🚫 dangerJS against 839b96d

@antonis
Copy link
Contributor Author

antonis commented Nov 25, 2025

@sentry review

@@ -0,0 +1,104 @@
/**
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test file location at packages/core/test/typings/object-freeze.test.ts may not be picked up by Jest's testPathIgnorePatterns in jest.config.js, which currently ignores <rootDir>/test/typings/ directory (note the different directory structure). Verify that this test file is actually executed by the test suite. If the intent is to have type-checking tests ignored from runtime testing, consider either updating the Jest configuration or moving the test to a location that matches the configured patterns.
Severity: MEDIUM

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/core/test/typings/object-freeze.test.ts#L1

Potential issue: The test file location at
`packages/core/test/typings/object-freeze.test.ts` may not be picked up by Jest's
`testPathIgnorePatterns` in `jest.config.js`, which currently ignores
`<rootDir>/test/typings/` directory (note the different directory structure). Verify
that this test file is actually executed by the test suite. If the intent is to have
type-checking tests ignored from runtime testing, consider either updating the Jest
configuration or moving the test to a location that matches the configured patterns.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 3552648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants